Skip to content

[azure-build-cache] Expose loginFlowFailover in build-cache schema#5274

Merged
dmichon-msft merged 2 commits intomicrosoft:mainfrom
dmichon-msft:login-flow-failover
Jul 12, 2025
Merged

[azure-build-cache] Expose loginFlowFailover in build-cache schema#5274
dmichon-msft merged 2 commits intomicrosoft:mainfrom
dmichon-msft:login-flow-failover

Conversation

@dmichon-msft
Copy link
Contributor

Summary

Updates the azureBlobStorageConfiguration section of the Rush build-cache.json schema to allow all valid values for loginFlow and to support configuration of loginFlowFailover to specify what order to try authentication providers in.

Details

loginFlow supports the following values:

  • 'DeviceCode'
  • 'InteractiveBrowser'
  • 'AdoCodespacesAuth'
  • 'VisualStudioCode'
  • 'AzureCli'
  • 'AzureDeveloperCli'
  • 'AzurePowerShell'

The loginFlowFailover field is an object that maps valid loginFlow types to other loginFlow types as the next fallback option. If no entry is defined for a given loginFlow, failures in that login flow will be terminal.

How it was tested

Locally configured the azure-blob-storage provider in build-cache.json and tried out different values of loginFlow and loginFlowFailover with the rush update-cloud-credentials --interactive command.

Impacted documentation

The schemas.

@dmichon-msft dmichon-msft enabled auto-merge (squash) July 9, 2025 21:57
@dmichon-msft dmichon-msft disabled auto-merge July 10, 2025 00:08
@dmichon-msft dmichon-msft enabled auto-merge (squash) July 10, 2025 00:08
@dmichon-msft dmichon-msft force-pushed the login-flow-failover branch from 75f064f to 396053e Compare July 12, 2025 01:14
@dmichon-msft dmichon-msft merged commit 50727f8 into microsoft:main Jul 12, 2025
5 checks passed
@github-project-automation github-project-automation bot moved this from Needs triage to Closed in Bug Triage Jul 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Closed

Development

Successfully merging this pull request may close these issues.

4 participants